2016-08-18 - 26998 - Spec - Incoterms and Port values in CHR IDOC #abapidoc #chr

SPECIFICATIONS

26998-Spec-Incoterms and Port Values in CHR IDOC


Purpose


Incoterms and Port Values in CHR IDOC

Admin Info


Purpose
Incoterms and Port Values in CHR IDOC
Requested By
Jingsha
Spec Created By
Adithya
Spec Created Date
08/18/2016
Spec QA by
Adithya
Objects
ZXM06U33
Document Status
Complete

Estimates


Sl.No
Activity
Estimation in Hours
1
Research

2
Documentation
08
3
Development/ Config
08
4
Unit test in DEV
12
5
Unit test in QUA

6
Other activity


TOTAL
28
References

Prior Tickets

[Provide links of prior associated Spec / Break Fix BOSS document(s)]
2016-07-14 - 26998 - Spec - CH Robinson New Output type ZCHR

Documents

[Attach any document(s) received for the requirement(s)]

Spec Changes


[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]

Sl.
Change Details
Requested By
Requested On
Notes if any





Functional Requirement


Purpose/WHY:

[Explain the purpose of the project and the reason why this requirement has come]
Incoterms which are there in the CHR PO are pulled in to the IDOC for the NB Purchase Orders where as for The Purchase Orders which have the sales orders the case is different

For Z3NB Purchase Order / NB TAB Purchase Order.
Header Incoterms:
1. If the Purchase Order is having Single Sales order then the Incoterms and Port are pulled from Sales Order.
2. If the Purchase Order is having Multiple Sales orders then the Incoterms and Port are pulled from Purchase Orders in the IDOC.
Item Incoterms:
If the PO is having multiple sales order or single, The Incoterms and port values are pulled from the sales order in the IDOC.

Requirement:
Regardless whether the PO is standard PO or 3rd party PO, INCO terms and the related Port should always be populated in the IDOC from the PO header.

In Scope:

[List the activities to be included in scope]
Incoterms in the PO Header.
This change is applicable to both ORDERS and ORDCHG for ZCHR message type.

Out of Scope:

[Out of scope activities]
Incoterms in the PO Item
Incoterms at the item level would still come from the sales order for the NB TAB and Z3NB POs


Got Information
Incoterm data of the PO Item also shall be considered for this change ?
No
Which value shall be picked in the IDOC if the Incoterms and port values are blank in the Purchase Order ?
Blank - No Segment

Solution Summary


[Discuss this section with Requester and get approval prior to beginning work]
Enhance the IDOC so as the data for Incoterms and Port values shall be picked from the Purchase Order rather than the sales order.

Test Plan

[List test scenarios/cases to be executed here]
Test ID
Test Scenario
Expected Results
IDCO1
Create a PO with single Sales Order
1. NB TAB
2. Z3NB
Incoterms and related port shall be picked from the Header from the Purchase order in the IDOC
IDOC2
Create a PO with Multiple Sales Orders
1. NB TAB
2. Z3NB
Incoterms and related port shall be picked from the Header from the Purchase order in the IDOC
IDOC3
Change a PO with single Sales Order
1. NB TAB
2. Z3NB
Incoterms and related port shall be picked from the Header from the Purchase order in the IDOC
IDOC4
Change a PO with Multiple Sales Orders
1. NB TAB
2. Z3NB
Incoterms and related port shall be picked from the Header from the Purchase order in the IDOC
IDOC5
Create a standard PO
Incoterms and related port shall be picked from the Header from the Purchase order in the IDOC
IDOC6
Change the Standard PO
Incoterms and related port shall be picked from the Header from the Purchase order in the IDOC
IDOC7
Create a 3rd part PO with Blank data in the Incoterms Header and Item

Solution Details

[Provide complete technical details for configuration or programming here]
Modify User Exit 'ZXM06U33' to overrite the Incoterm and Port value which is pulled from Sales Order with Incoterm and port value from Purchase Order. If Purchase Order values are blank then that information should not be included in IDOC.
This change is applicable to both Idoc types ORDERS and ORDCHG for ZCHR message type.

Issues

[List Issues / Bugs identified in configuration or development]